Only available for Logged-in member. Please login or register to access this information.Or use the Temporary User that we have provided to you via email.
expiry time
Item codes | FW Released Date | Changes Information |
|---|---|---|
WSLRW-SL-01S-OP | 16/12/2025 | Initial firmware |
1
QUICK INSTALLATION GUIDE
1.1 Introduction
WSLRW-SL is a LoRaWAN noise sensor with a measuring range of 30-120 dB(A) for residential, office, factory, construction sites, and public areas... Capacitive technology has high sensitivity, accuracy, and stability. LoRaWAN connectivity enables kilometer-long data transmission to LoRaWAN Gateways. With an ultra-low power design and intelligent firmware, the sensor can operate for up to 10 years with only 2 AA batteries (depending on configuration), or use solar panels for applications of continuous monitoring. The device supports all LoRaWAN bands worldwide.
How the sensor connect to system?
System components:
The end nodes are LoRaWAN Sensors or Actuators;
The Gateways are LoRaWAN Gateway or Base Station;
The Network Server can be SAAS or On-premise server;
The Application Server is the destination software users want to utilize the data from/ to LoRaWAN sensors/ actuators.
How to set up the LoRaWAN system? Please follow these steps:
Adding the Gateways to a Network server. Please refer to the manual of Gateway and Network Server software;
Adding the End nodes to the Network Server;
Configure the callback or data forwarding from the Network Server to the Application Software by MQTT or HTTPS. Please refer to the manual of the Network Server.
Once the payload is on the Application server, decode data from Payload. Please check Section 1.9 for the Payload document.
1.2 Application Notes
For Applications
Ambient Air Quality Monitor, Facility Monitoring, Machine Health Monitoring, Safety Monitoring
Notes
Sensitivity: Match to environment (high for quiet, low for noisy).
Frequency Response: Ensure required range (e.g., 20 Hz–20 kHz for audio).
Environmental Protection: Dust/moisture sealing, EMI shielding for harsh conditions.
1.3 When does device send Uplink messages?
The device will send uplink messages in the following cases:
Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device.
Case 2: Then, in every interval time (pre-configured), for example, 30 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...
To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.
Case 3: If ALARM_ENABLED=1, the device will send ALARM message immediately when device switches from Normal state to Alarm state. It will repeat sending ALARM messages in predefined ALARM_PERIOD time interval if the Alarm state still exist.
Case 4: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s.
Case 5: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.
Case 6: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 7: If LNS_CHECK_MODE =1, it will send the confirmed uplink message called LNS_CHECK every 24 hours. This confirmed uplink message is a message where a LoRaWAN device is requesting a LoRaWAN network to confirm the reception of its message. If the device receives no confirmation message from LoraWAN network server, it will re-send the LNS_CHECK message every hour during 3 hours. After 4th hour, if the device still receives no confirmation message, it will reset itself to join the network server. The LNS_CHECK payload will tell the user the following data like hardware version, firmware version, current sensor configuration.
Case 8: If the application/network server sends downlink 3 to check current value of a configuration parameter or sends downlink type 5 to change value of a configuration parameter, the device will send the CONFIG-CHECK uplink. The payload of CONFIG-CHECK uplink contains the result of the configuration changes/configuration check.
1.4 Default Configuration
The SL sound level sensor has the default configuration. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Below are some configuration parameters that store in the flash memory of the wireless transmitter.
1.5 Battery/ Power Supply
The Device uses Solar Panel with an M12-Male connector, 6V, PU coated, ETFE coated, tilt adjustment, 1/2" pipe mount.
To allow the device to run during the time without the Sun, please insert 02 rechargeable batteries as below into the battery holders.
Battery type: Rechargeable, size AA
Number of batteries: 02
Battery voltage: 1.2V
Recommended batteries: Panasonic Eneloop BK-3MCCE or Fujitsu HR-3UTC
Please take note on the Polarity of the batteries as below picture.
Understanding the Battery Levels:
Level 3 (4 bars): battery energy is 60-99%
Level 2 (3 bars): battery energy is 30-60%
Level 1 (2 bars): battery energy is 10-30%
Level 0 (1 bar): battery energy is 0-10%
Note: To display accurately the remaining energy of battery, please configure the correct BATTERY_TYPE by downlink type 5 or offline cable. Please check the section "Principle of Operation" for more details.
1.6 What's in the Package?
1.7 Guide for Quick Test
With the default configuration, the device can be connected quickly to the Network Server by the following steps.
Step 1: Prepare the values of communication settings
Frequency zone: Most of the sensor was configured the frequency zone to suit customer application before delivery
DevEUI: Get the DevEUI on the product nameplate
AppEUI Default value: 010203040506070809
AppKey Default value: 0102030405060708090A0B0C0D0E0F10
Activation Mode: OTAA with local join server
Network Mode: Public
LoraWAN Protocol: version1.0.3
Class: A for sensor; C for actuator
If current basic common settings do not match with your region, network server/application, follow below instruction to change them as below:
NOTE: If the settings in above table are changed via downlink, the device MUST be reset to make the changed settings take effect. The reset is hard reset (Turn OFF external power supply, wait 3-7 minutes, and then turn ON external power supply OR take out battery, wait 3-7 minutes and then insert battery back ) OR soft reset via downlink 0. Downlink 0 hexadecimal value to reset device equal CURRENT_CONFIGURATION hexadecimal value in uplink but change the 15th value of the CURRENT_CONFIGURATION from 0 to A. For example, CURRENT_CONFIGURATION is 00C80064000B6000, the downlink 0 value for resetting device will be 00C80064000B60A0
For changing other settings, please refer to Section 3.2 Sensor configuration to change the other settings
Step 2: Register the device on the LoRaWAN network server
Input the above settings on your device registration page of the network server.
Note: Different network server software will have different device registration processes. Please refer to the manual of the network server software used for more details.
Please visit the below Section 1.10 to get the instructions for adding the LoRaWAN sensors to some common network servers such as Actility, TTN...
Step 3: Install the batteries to the device OR do power wiring and supply external power to the device if applicable
Please refer to Section 1.5 as above for instructions on battery installation OR for instructions to do power wiring and supply external power to the the device if applicable
After installing the battery in 60 seconds, the first data packet will be sent to the LoRaWAN gateway. After receiving the first data packet, the time of another packet depends on the value of the parameter: cycle_send_data. Additionally, you can use a magnet key to touch the magnetic switch point on the housing within 1 second to initiate force packet of the device to send data instantly and the LEDs on the housing will be lit with SKY BLUE color.
Step 4: Decode the payload of receiving package
Please refer to Section 1.9 Payload Document and Configuration Tables for details of decoding the receiving packet to get the measured values.
If the device has local display, measured values are shown on the local display
1.8 Installation
Dimension Drawings and Installation Gallery (Photos and Videos)
Please follow the checklist below for a successful installation:
1. Have you studied the dimensions of the device as above drawings?
2. Have you tested and make sure the device have been connected successfully as Section "1.7 Guide for Quick Test" above?
3. Have the device been configured properly as per Section 3.2 below?
4. Have the device been calibrated or validated as per Section 3.3 below?
5. Then you can start to install the device at site. Please check the following Installation Notes for Sensor Part (if available) before installation.
Installation Notes for Sensor Part (if available)
Installation notes for sound sensors to be considered:
1. Placement
* Mount away from strong airflow, vibration, and direct sunlight.
* Position close to the sound source for accurate detection.
* Avoid enclosed spaces that cause echo or resonance.
2. Orientation
* For directional microphones, point toward the sound source.
* For omnidirectional sensors, ensure unobstructed surroundings.
3. Wiring
* Use shielded cables for analog signals to reduce noise.
* Keep signal wires short and away from power lines.
* Follow polarity markings for power and signal pins.
4. Environmental Protection
* Use IP-rated enclosures for outdoor or dusty environments.
* Apply acoustic vents for waterproofing without blocking sound.
Installation Guide for Main Device
Check the Location for the best RF Signal
Make sure the site is good enough for RF signal transmission.
Tip: To maximize the transmission distance, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and the LoraWAN gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with the Gateway, but the distance will be reduced significantly.
DO NOT install the wireless sensor or its antenna inside a completed metallic box or housing because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.
Mounting the Device on the Wall or Pole
Install the solar panel to the available frame with provided accessories
Mount the device onto a wall/pole/object by the provided screws via two holes on the devices
Adjust angle of solar panel for optimized solar energy: Depending on the location of the site, the solar panel needs to be adjusted with the Tilt angle and Azimuth angle so that it can receive the most energy from the Sun in the entire year.
Insert 2 x chargeable 1.2 V batteries to the device
Plug M12 cable of solar panel to M12 connector of the device
1.9 Payload Document and Configuration Tables
Please click below button for:
-
Payload decoding of Uplink messages;
-
Payload encoding of Downlink messages;
-
Configuration Tables of device.
Note:
If the content of below web payload, memory map, and sample decoder could not be copied, please install the extension of "Enable Copy Paste - E.C.P" for Microsoft Edge and for Google Chrome.
1.10 How to connect device to Back-end/ Network Server/ Coordinator
Please find below the examples of adding Daviteq's LoRaWAN sensor to the following Network servers:
ThingPark Community (of Actility);
Things Stack (of The Things Network).
You can use the similar methods to add LoRaWAN sensors to other Network Server.
1. THINGPARK COMMUNITY (ACTILITY) NETWORK SERVER
1.1. Example to add the Tektelic LoraWAN gateway Model T0005204 to ThingPark Enterprise SaaS Community
1. Log in to your ThingPark Enterprise account via the link: https://community.thingpark.io/tpe/
2. Browse on the left panel to Base Stations, click the drop-down menu, then click Create.
3. Select the base station’s Tektelic.
※ If you do not find the Tektelic, click View More Manufacturers.
4. On the following screen, select the Model: Micro 8-channels from the drop-down list.
5. Fill the form as below table:
Input exactly as above Input field column, except Name field is user-defined and is different from the existing base station name on the network server.
After filling the registration form, click CREATE to complete adding the base station to the network server.
1.2. Add Daviteq's LoRaWAN devices to ThingPark Enterprise SaaS Community
ThingPark Enterprise supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server that is programmed at the factory.
Manual provisioning of OTAA devices using a local Join Server. To learn more, see Activation modes.
1. At left panel of the screen of the Thingpark GUI, click Devices > Create from the dashboard.
2. Select the Generic supported by your device on your screen.
3. Select the Model of LoRanWAN 1.0.3 revA - class A with correct frequency plan
4. Fill the form as below table:
In addition to filling out the form, the option to select the connection between ThingPark and Daviteq application (Globiots).
After filling out the registration form, please click CREATE to add devices to the network server.
1.3. Send a downlink frame from Thingpark Network Server to the device
Follow the below steps to send the downlink frame from Thingpark Network Server to the device:
This functionality is active only when a connection is associated to the device (one of the color codes with a green bullet).
1. Navigate to the left panel, click the Devices' drop-down menu, then click List.
2. Browse the right side in the Devices, click the icon of the device and click Send Downlink.
3. Input the downlink code to the Payload field and input 1 to the Port field, and then click Validate.
The downlink data is added to the device downlink queue in network server. The downlink is sent after the network server receive an uplink from the device.
2. THINGS STACK (THE THINGS NETWORK) NETWORK SERVER
2.1. Add Sentrius LoraWAN gateway (Model RG19) to The things Stack network server
1. Log in to you’re The Things Stack account
2. Click the tab Gateways, click Add gateway button
3. Fill out the form as below table:
Input exactly as above Input column, except the Gateway Name field and the Gateway ID field is user-defined. It is different from the existing gateway name and gateway ID on the network server.
After filling the registration form, click Create gateway to complete adding the base station to the network server.
2.2. Add Daviteq's LoRaWAN device to The Things Stack network server
The Things Stack supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server programmed at the factory.
1. Browse on the top panel, click the tab Application, and click Add application button to create an application
2. Fill in the information fields as user-defined, then select Create application
3. After the application is created successfully, select Add end device to register end device (LoRaWAN sensor)
4. Fill out the form as below table:
After filling out the registration form, please click the Register end device button to add the device to the network server.
2.3. Send a downlink frame from The Things Stack Network Server to the device
1. Select the device to send downlink
2. Input 1 to the FPort and input the downlink data in the payload field, and then tick Confirmed downlink and click Schedule downlink.
2
MAINTENANCE
2.1 Troubleshooting
Please find below steps to identify the problems from Communication Part or Sensor Part:
* If the device cannot connect to the Gateway or System or Co-ordinator at the first time, it is the Communication Problem;
* If the device status like battery, RSSI level, data status or other communication is normal, but the measured values are not updated or wrong, it would be the problems of Sensor part;
* If the data coming to gateway, system or co-ordinator is not frequently as expected, the problem would be Communication.
Please refer below the troubleshooting guide for Communication and Sensor Part.
Troubleshooting for Communication
Troubleshooting for Sensor Part (if available)
Troubleshooting tips for sound sensors:
1. No Output Signal
* Check Power: Verify correct voltage and stable supply.
* Inspect Wiring: Ensure proper connections and polarity.
* Test Sensor: Use a multimeter or oscilloscope to confirm output.
2. Weak or Inaccurate Response
* Sensitivity Setting: Adjust potentiometer (if available).
* Placement: Move sensor closer to sound source; avoid obstructions.
* Noise Filtering: Add low-pass filter or shield cables.
3. False Triggering
* Environmental Noise: Reduce background noise or use directional microphones.
* Threshold Adjustment: Increase detection threshold in firmware or hardware.
* Isolation: Mount sensor away from vibration sources.
4. Distorted Signal
* Overload: Reduce gain or use attenuator if sound is too loud.
* Cable Issues: Replace damaged or unshielded cables.
* Grounding: Ensure proper grounding to avoid interference.
5. Communication Errors (Digital Sensors)
* Protocol Check: Confirm I²C/SPI settings match MCU.
* Pull-up Resistors: Verify presence for I²C lines.
* Firmware Update: Ensure correct driver and sampling rate.
2.2 Maintenance
Maintenance for Main device
There is no requirement for maintenance of the Hardware of LoRaWAN Device except:
The battery needs to be replaced. Please check the battery status via uplink messages;
Note: When the battery indicator shows only one bar (or 10% remaining capacity), please arrange to replace the battery with a new one as soon as possible. If not, the battery will drain completely, and the resulting chemical leakage can cause severe problems with the electronic circuit board.
Sensor, please refer to the maintenance section of the sensor document.
The Solar Panel needs to be cleaned periodically, depending on the particulate environment;
The mounting bracket of the Solar Panel needs to be verified to make sure the Solar panel is always in the correct tilt angle and azimuth angle;
Maintenance for Sensor part (if available)
Maintenance guidelines for sound sensors:
1. Regular Cleaning
* Remove dust and debris from the sensor surface and acoustic vents.
* Use a soft brush or compressed air; avoid liquids.
2. Check Connections
* Inspect wiring for loose or corroded contacts.
* Verify cable shielding to prevent noise interference.
3. Calibration
* Periodically calibrate sensors used for dB measurement to maintain accuracy.
* Use a reference sound source or calibration device.
4. Firmware Updates
* For digital sensors, keep firmware and drivers up to date for compatibility and performance.
5. Environmental Protection
* Ensure seals and enclosures remain intact for outdoor installations.
* Replace acoustic membranes if damaged.
6. Functional Testing
* Test sensor response with a known sound source.
* Monitor output for drift or abnormal readings.
3
ADVANCED GUIDE
3.1 Principle of Operation
Principle of Operation for device WSLRW-SL | FW1
Device components
Daviteq LoRaWAN sound level sensor comprises 02 parts linked internally:
• The Daviteq LoraWAN wireless transmitter;
• The Daviteq sound level sensor
What are the primary output values?
• RAW SOUND LEVEL: Raw value of sound pressure level to calculate SPL (Sound Pressure Level);
Sound pressure level = CONSTANT_A * RAW_SOUND_LEVEL + CONSTANT_B.
This parameter equals RAW_SOUND_LEVEL_X10 in the uplink payload divided by 10
• SPL: Sound Pressure Level, unit of dB. This parameter equals SPL_X10 in the uplink payload divided by 10
• LEQ: Equivalent Continuous Sound Pressure Level (LEQ), unit of dB, used for alarm, the single-value metric used to describe a fluctuating noise level over a specified period of time. This parameter equals LEQ_X10 in the uplink payload divided by 10
What are the secondary output values?
Below output values are useful for device maintenance and troubleshooting.
• HW VERSION: Hardware version. This parameter equals HW_VERSION in the uplink payload
• FW VERSION: Firmware version. This parameter equals FW_VERSION in the uplink payload
• CURRENT CONFIGURATION: Latest received and valid downlink 0 frame. It is CURRENT_CONFIGURATION on device memory map. Detail of CURRENT_CONFIGURATION is at G. MODBUS MEMORY MAP section. This parameter equals CURRENT_CONFIGURATION in the uplink payload
• SENSOR COM ERROR: Communication error code for sensor. This parameter equals SENSOR_COM_ERROR in the uplink payload
• ALERT STATUS: Alert status. This parameter equals ALERT_STATUS in the uplink payload
• POWER LEVEL: Power supply level (battery or external power). This parameter equals POWER_LEVEL in the uplink payload
• POWER SOURCE: Power source (battery or external power). This parameter equals POWER_SOURCE in the uplink payload
• TENTATIVE: The number of continuous alarm cycles. If the number of continuous alarm cycles is greater than 255, the Tentative keep value of 255. This parameter equals TENTATIVE in the uplink payload
• START ADDRESS: The start address of the configuration to check. This parameter equals START_ADDRESS in the uplink payload
• NUM OF REGISTER: Number of register of the configuration to check. This parameter equals NUM_OF_REGISTER in the uplink payload
• CONTENT OF REGISTER: Content of configuration, in hexadecimal format. This parameter equals CONTENT_OF_REGISTER in the uplink payload
Principle of operation
Most of the time, the device will be in sleep mode. When the timer reaches the Measure_Period (for example, 30 minutes), it will wake up the device to start the measurement.
*** This Measure_Period will affect the energy consumption of the device.
The measurement will take a certain time to finish; it can take milliseconds or seconds to finish the measurement. This measurement time depends on sensor type, required accuracy, and other factors. Shorter measurement time, lower energy consumption, and longer battery life.
After finishing the measurement cycle, the device can read all the measured parameters.
Main parameter for alarm is LEQ
If parameter ALARM_ENABLE = 1
Then the device will compare the main parameter to HiHi_Alarm_setpoint and Hi_Alarm_setpoint together with Hysteresis to define the state of the device is No_Alarm or Hi_Alarm or HiHi_Alarm.
Hysteresis value is to avoid the flickering status (Alarm/No-Alarm toggling quickly) when the measured value close to alarm threshold. This device, the hysteresis is zero (fixed value).
If value of main parameter is in Blue color area of above graph, the device is in Normal or No_Alarm state;
If value of main parameter is in Red color area, the device is in HiHi Alarm state (Alarm 2);
None of above 02 states (in Yellow color area), the device will be in Hi Alarm state (Alarm 1).
How the device send uplink message base on above 03 states?
If Device state is No_Alarm, it will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;
If Device state is changed from No_Alarm to Hi Alarm or HiHi Alarm, it will send alarm message immediately.
Please check the below picture to understand the operation flow when finishing the measurement cycle:
Once the alarm happens and send the first alarm message, the device will send the next alarm message in the Alarm_Period if the device is still in Alarm states (Hi Alarm or HiHi Alarm), and TENTATIVE value will increase one unit . Please check the picture below to understand the operation flow when the Alarm timer reaches the Alarm_Period. Alarm_Period is fixed value of 10 minutes.
If parameter ALARM_ENABLE = 0
The device will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message.
Please check the Payload document to understand clearly uplink messages, downlink messages, meaning of parameters for configuration...
Power saving mode
When the device power supply voltage is less than STOP_VOLT_THRESHOLD_W_PASSWORD (default of 2.42 V, POWER_LEVEL =2 at this voltage), the device will operate in power saving mode. In this mode, the device stops measuring, stops sending FORCE uplink, CYCLIC_DATA uplink and ALARM uplink and send HEARTBEAT uplink with period of NO_MEASURE_HEARTBEAT_PERIOD (default of 1800 seconds). When the device is in power saving mode and device power supply voltage is greater than STOP_VOLT_THRESHOLD_W_PASSWORD (default of 2.42 V) plus RESUME_VOLT_OFFSET_W_PASSWORD (default of 0.07 V), the device will return to normal mode.
Alarm configurations
UNSCALED_HIHI_ALARM_SETPOINT: Unscaled too high alarm set point to calculate HIGHHIGH_ALARM_SETPOINT for LEQ, unit of dB
UNSCALED_HI_ALARM_SETPOINT: Unscaled high alarm set point to calculate HIGH_ALARM_SETPOINT for LEQ, unit of dB
HIHI_ALARM_FACTOR: Too High alarm factor to calculate HIGHHIGH_ALARM_SETPOINT
HI_ALARM_FACTOR: Hi alarm factor to calculate HIGH_ALARM_SETPOINT
ALARM_ENABLE: Enable/Disable ALARM event
ALARM_PERIOD: Period of time to send ALARM event
HIGHHIGH_ALARM_SETPOINT: Too high alarm threshold for LEQ, unit of dB
*If HIHI_ALARM_FACTOR <= 7
HIGHHIGH_ALARM_SETPOINT = UNSCALED_HIHI_ALARM_SETPOINT *(10^HIHI_ALARM_FACTOR)
*If HIHI_ALARM_FACTOR >=8
HIGHHIGH_ALARM_SETPOINT = UNSCALED_HIHI_ALARM_SETPOINT / (10^(16-HIHI_ALARM_FACTOR))
HIGH_ALARM_SETPOINT: High alarm threshold for LEQ, unit of dB
*If HI_ALARM_FACTOR <= 7
HIGH_ALARM_SETPOINT = UNSCALED_HI_ALARM_SETPOINT * (10^HI_ALARM_FACTOR)
*If HI_ALARM_FACTOR >=8
HIGH_ALARM_SETPOINT = UNSCALED_HI_ALARM_SETPOINT / (10^(16-HI_ALARM_FACTOR))
LEDs & buzzer descriptions
Communication LED (COM): will lit in short time when the device is sending a uplink. The color of the LED is based on sent uplink type. Please refer section 1.9 Payload and Configuration Tables for details of color
Charge LED (CHARG): will lit when the device is charged by external power supply/solar panel
Principle of Operation of Sensor part (if available)
The operation principle of a sound sensor is based on the conversion of mechanical sound waves into measurable electrical signals. It acts essentially as an electronic "ear," translating air pressure variations into voltage.
1. The Core Mechanism: The Transducer
At the heart of every sound sensor is a microphone (usually a condenser or electret microphone) that acts as a transducer.
* Vibration Capture: Sound travels as longitudinal waves (cycles of compression and rarefaction). When these waves hit the sensor, they strike a thin, flexible diaphragm.
* Capacitance Change: In a condenser microphone, the diaphragm acts as one plate of a capacitor, held close to a fixed backplate. As sound causes the diaphragm to vibrate, the distance between the plates changes.
* Signal Generation: Because the distance changes, the capacitance fluctuates. According to the formula , if the charge () is constant and capacitance () changes, the voltage () must change accordingly. This creates a tiny, fluctuating electrical signal that mirrors the original sound wave.
2. Signal Processing (The Module Level)
A standard sound sensor module does more than just "hear"; it processes the signal to make it usable for microcontrollers.
Microphone: Converts sound pressure into a tiny AC voltage.
Amplifier (Op-Amp): Boosts the millivolt-level signal from the microphone to a range the controller can read.
Potentiometer: A trimmer resistor used to set a "threshold" or sensitivity level for detection.
Comparator: Compares the amplified sound signal against the threshold to produce a Digital Output.
3. Output Types
Most modules provide two types of outputs to satisfy different project needs:
* Analog Output (AO): Provides a continuous real-time voltage signal. The voltage level directly corresponds to the intensity of the sound. This is used when you need to measure volume or process specific audio patterns.
* Digital Output (DO): Acts as a switch. When the sound level exceeds the threshold set by the potentiometer, the pin flips from HIGH to LOW (or vice versa). This is ideal for "clap switches" or simple noise triggers.
* RS485 serial port output: the signal is digitalized and send via RS485 serial port
4. Summary of Operation Steps
1. Acoustic Input: Sound waves travel through the air.
2. Mechanical Vibration: The microphone diaphragm moves in response to air pressure.
3. Transduction: Mechanical movement is converted into a weak electrical signal.
4. Amplification: The internal circuitry increases the signal strength.
5. Conditioning: The module outputs either the raw wave (Analog), RS485 serial port or a trigger pulse (Digital).
Default Configuration Parameters of Sensor part (if available)
The SL sound level sensor has the default configuration. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Below are some configuration parameters that store in the flash memory of the wireless transmitter.
3.2 Configuration
How to configure the device?
Sensor configuration can be configured in 02 methods:
Method 1: Configuring via Downlink messages, port 1 (default)
Method 2: Configuring via Offline cable.
Access the device's configuration port: Open the housing by unscrewing 2 hex nuts, pull out the housing and the position of the sensor's configuration port as below figure:
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
Which Parameters are configured?
Please check Part G in Section 1.9 Payload Documents above.
Method 1: Configuration via Downlink messages
Please check the Part D & E in Section 1.9 Payload Documents above.
Method 2: Configuration by Offline Cable
Please download the Configuration Template File of this sensor to be used in Step 4 below.
Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.
Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.
1. Prepare equipment and tools
The following items must be prepared for configuration.
A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
A Modbus configuration cable
Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)
2. Download and launch Daviteq Modbus configuration software
Click the link below to download Daviteq Modbus configuration software:
https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs
After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use.
Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:
Note: The software only runs on Microsoft Windows OS (Windows 7 and above).
3. Connect the cable and configure the sensor
Step 1:
Connect the PC to the sensor using the configuration cable.
- Use the configuration cable (Item code: TTL-LRW-USB-01).
- Connect the USB-A plug into the USB-A socket of the PC.
Step 2:
On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none
Step 3:
Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.
Step 4:
Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.
Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.
Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.
Step 5:
Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.
Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type
Note: If the sensor has SKU of WSLRWEX-PPS and hardware version 1 & 2, the sensor must be powered by batteries for configuration
Step 6:
Read the current value of the parameter with Modbus Function 3
At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
Step 7:
Write the new setting to the parameter with Modbus Function 16
Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;
Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.
Repeat Step 6 to read the setting of the parameter for double-checking.
Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.
Only read/ write registers are allowed to write.
The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.
4. Troubleshooting
3.3 Calibration/ Validation
How to force sensor to send data for calibration/ validation (if available)
Using the magnet key, the device can be triggered to send data to the LoRaWAN gateway immediately.
Note:
Upon transmitting the data to the gateway using the magnetic key, the timer for the transmission time interval will be reset.
The minimum time interval between two manual triggers is 15 seconds. If the interval is less than 15 seconds, data transmission will not occur.
Calibration/ Validation sensor (if available)
The sensor could be calibrated by below steps:
Change current CONSTANT_A to 1 and CONSTANT_B to 0. At this time the raw sound level will equal scaled sound level
Connect directly the probe of sound sensor to output of standard sound generator
Switch 2 positions of sound generator to generate 2 standard levels and record sensor-sound level
Calculate CONSTANT_A, CONSTANT_B based on 2 standard sound level and 2-recorded sound level
Write calculated CONSTANT_A, CONSTANT_B to the sensor
4
PRODUCT SPECIFICATIONS
4.1 Specifications
Spec
5
WARRANTY & SUPPORT
5.1 Warranty
Warranty
Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.
Free Warranty Conditions
The manufacturer undertakes to guarantee within 12 months from shipment date.
Product failed due to defects in material or workmanship.
Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.
Note: One way shipping cost to the Return center shall be paid by Customers.
Paid Warranty
The warranty period has expired.
The product is not manufactured by Daviteq.
Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
Product damaged during shipment.
Product damaged due to faulty installation, usage, or power supply.
Product damage caused by the customer.
Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
Product damage is caused by unauthorized treatments and modifications.
Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.
5.2 Support
Support via Help center
If you need our support for Daviteq device's installation, configuration, test, and decode, please input support request at link: https://forms.office.com/r/XWHbYG7yy7
Our support engineer will contact you via email or the support ticket system.
If you have any questions about the product, you can search for information on our web (https://www.iot.daviteq.com/). If you can't find the right information, please register an account and send us a request at link Contact us | Daviteq Technologies . We will respond within 24 hours.